🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Locate and show the relevant portion of the OpenResty runtime script
FILE=".github/scripts/run-openresty-runtime.sh"
test -f "$FILE" || { echo "Missing $FILE"; exit 1; }

echo "=== $FILE (head/tail around suspected lines) ==="
nl -ba "$FILE" | sed -n '1,120p'

echo
echo "=== Search for busted references in the repo ==="
rg -n --hidden --no-ignore-vcs "BUSTED|busted" .github || true

echo
echo "=== Search workflows/jobs that run 'busted' ==="
rg -n --hidden --no-ignore-vcs "run-openresty-runtime\.sh|openresty-runtime|busted" .github/workflows || true

Repository: api7/lua-qjson

Length of output: 203

🏁 Script executed:

#!/bin/bash
set -euo pipefail

FILE=".github/scripts/run-openresty-runtime.sh"
test -f "$FILE" || { echo "Missing $FILE"; exit 1; }

echo "=== $FILE (first 120 lines) ==="
awk '{printf "%d:%s\n", NR, $0}' "$FILE" | sed -n '1,120p'

echo
echo "=== $FILE (lines 20-80) ==="
awk '{printf "%d:%s\n", NR, $0}' "$FILE" | sed -n '20,80p'

echo
echo "=== Search for busted references in the repo ==="
rg -n --hidden --no-ignore-vcs "BUSTED|busted" .github || true

echo
echo "=== Search workflows/jobs that run this script ==="
rg -n --hidden --no-ignore-vcs "run-openresty-runtime\.sh|openresty-runtime" .github/workflows || true

echo
echo "=== Show any job step that runs busted directly (workflows) ==="
rg -n --hidden --no-ignore-vcs "busted" .github/workflows || true

Repository: api7/lua-qjson

Length of output: 4426

🏁 Script executed:

#!/bin/bash
set -euo pipefail
FILE=".github/workflows/ci.yml"
test -f "$FILE"
awk 'NR>=150 && NR<=420 {print NR ":" $0}' "$FILE" | sed -n '1,350p'

Repository: api7/lua-qjson

Length of output: 10140

🏁 Script executed:

#!/bin/bash
set -euo pipefail
FILE=".github/workflows/ci.yml"
test -f "$FILE"
awk 'NR>=150 && NR<=420 {print NR ":" $0}' "$FILE" | sed -n '1,350p'

Repository: api7/lua-qjson

Length of output: 10140

🌐 Web query:

OpenResty Docker image /usr/local/openresty/luajit/bin/busted exists

💡 Result:

In the official OpenResty Docker images (openresty/openresty), the file path /usr/local/openresty/luajit/bin/busted is not something the image provides by default. What the image does provide by default is LuaJIT/luarocks at /usr/local/openresty/luajit/bin/luarocks (as documented in the docker-openresty repo README) [1]. The OpenResty image Dockerfile builds and installs LuaRocks, but it does not document installing the busted test runner into /usr/local/openresty/luajit/bin/busted [2]. Therefore, you should expect that /usr/local/openresty/luajit/bin/busted will be missing unless you install busted yourself (e.g., via luarocks) in your own Dockerfile or at container build time. If you specifically want, tell me which OpenResty image tag you’re using (e.g., openresty/openresty:1.27.1.2-0-bookworm-fat), and I can help craft the exact Dockerfile snippet to install busted in that image.

Citations:

• 1: https://github.com/openresty/docker-openresty/blob/master/README.md
• 2: https://hub.docker.com/r/openresty/openresty/dockerfile

🏁 Script executed:

#!/bin/bash
set -euo pipefail
FILE=".github/scripts/openresty-smoke.lua"
test -f "$FILE" && awk '{printf "%d:%s\n", NR, $0}' "$FILE" | sed -n '1,200p' || echo "Missing $FILE"

Repository: api7/lua-qjson

Length of output: 1018

🏁 Script executed:

#!/bin/bash
set -euo pipefail
FILE=".github/scripts/openresty-smoke.lua"
test -f "$FILE" || { echo "Missing $FILE"; exit 1; }
awk '{printf "%d:%s\n", NR, $0}' "$FILE" | sed -n '1,200p'

Repository: api7/lua-qjson

Length of output: 1018

🌐 Web query:

OpenResty resty command line LUA_PATH environment variable honored require package.path

💡 Result:

The OpenResty resty command does not automatically honor the shell environment variable LUA_PATH for Lua module resolution; instead it uses OpenResty/Lua’s lua_package_path/package.path setup that can be influenced via resty’s own CLI options (notably -I) and the nginx/OpenResty configuration it generates. What the resty CLI provides (authoritative): 1) resty has an -I DIR option specifically “Add dir to the search paths for Lua libraries.” [1][2] 2) The official demo shows resty -I lua/ -e 'require "test".hello()' and states: “Without the -I option, it won’t find it. This is because the lua/ directory is not in the Lua module search paths by default.” [3] 3) In the resty implementation, -I arguments are parsed and stored as include directories for Lua library search paths. [1] Implication for LUA_PATH: - Since the documented and implemented mechanism for adding Lua search locations with resty is -I (not LUA_PATH), and the demo explicitly frames the problem as “directory not in the Lua module search paths by default” unless you use -I, you should not rely on LUA_PATH being honored by resty’s require behavior. [1][3] Practical ways to make require work: A) Use resty -I: - Example pattern: resty -I /path/to/lua -e 'require "your.module"' [3] B) Or adjust OpenResty/Lua’s lua_package_path (nginx-side), since that’s what ultimately determines Lua’s package.path used by require: - In OpenResty nginx Lua module docs, lua_package_path is the directive that “set[s] search paths for pure Lua external libraries”. [4] Notes about “it sometimes seems to work” in containers: - There are reports that in some OpenResty Docker image variants, the container defines a LUA_PATH value and require may work when that path is consistent with the image’s configured Lua search paths. But this is image-specific behavior, not an advertised/guaranteed contract that resty honors LUA_PATH directly. [5]

Citations:

• 1: https://github.com/openresty/resty-cli/blob/master/bin/resty
• 2: https://github.com/openresty/resty-cli/blob/master/README.md
• 3: https://blog.openresty.com/en/resty-cmd/
• 4: https://github.com/openresty/lua-nginx-module/blob/master/README.markdown
• 5: Question about LUA_PATH openresty/docker-openresty#203

🏁 Script executed:

#!/bin/bash
set -euo pipefail
ls -la
test -f "lua/qjson.lua" && echo "FOUND lua/qjson.lua" || echo "MISSING lua/qjson.lua"
test -f ".github/scripts/openresty-smoke.lua" && sed -n '1,120p' .github/scripts/openresty-smoke.lua

Repository: api7/lua-qjson

Length of output: 2557

🌐 Web query:

Does the OpenResty resty CLI respect the LUA_PATH environment variable for package.path, or is --lua-path / -I required?

💡 Result:

The resty (OpenResty resty-cli) command does not appear to automatically honor the LUA_PATH environment variable to set Lua’s package.path; instead, you should use the resty CLI’s Lua path option (-I/--lua-path depending on version) to add search directories to Lua’s module search paths. Evidence: resty-cli documents that “-I DIR Add dir to the search paths for Lua libraries” [1][2], and its implementation builds a lua_package_path string from the provided -I directories (it generates lua_package_path "…"; and lua_package_cpath "…";) rather than reading LUA_PATH [3]. The generated nginx config snippet explicitly sets lua_package_path based on those include directories [3]. So, to ensure your Lua modules are found when running with resty, use -I/--lua-path (or the equivalent path-adding flag provided by your resty version) rather than relying on LUA_PATH being applied to package.path automatically.

Citations:

• 1: https://github.com/openresty/resty-cli/blob/master/README.md
• 2: https://github.com/openresty/resty-cli
• 3: https://github.com/openresty/resty-cli/blob/master/bin/resty